DiskFactory32Æs i/o thread requires less than 3% of the CPU resources û the 16 bit
version consumed nearly 90% of the CPU!
╖ X-Format media conversions:
The previous version ætrickedÆ the system into assumptions that preserved the original structure of the source, but often wasted much of the actual capacity of the Target.
DiskFactory32 now implements advanced algorithms that re-map the Source file system to the Target, providing these enhancements:
All remaining space on larger conversion targets is now usable
Larger-to-smaller conversions are now supported*
*(provided the Target capacity is sufficient to store all portions of the Source that are allocated by the file system)
╖ No Limitations on Source loaded from an Image file:
A Source loaded from diskette was treated preferentially by the previous version, which imposed restrictions on the ways an image file could be used. For instance, an image could not be used in a comparison, and Target image files could not be created from image file Sources
No limitations based on origin of Source data are ever imposed by DiskFactory32.
╖ Fewer limitations on Image file Targets:
Image file Targets are almost equivalent to diskettes too, though the following restrictions still apply:
An image file cannot be used as the Target for a Comparison. It is possible to compare an Image file to a diskette, by loading the Image file as the Source.
By definition, the previous limitation means that it is not possible for DiskFactory32 to compare an Image file to another Image file
DiskFactory32 will not allow a Format operation to be performed on an Image file Target.
╖ Allocated-Only, optimization option:
DiskFactory32 may now be configured to process only the areas of the diskette that have been allocated by the file system.
Substantial performance increase, when copying diskettes that are less than full.
The Allocated-Only feature is fully supported by X-Format conversions and Image files.
